Received: from onelist.com (pop.onelist.com [209.207.135.229])
by osf1.gmu.edu (8.8.8/8.8.8) with SMTP id EAA12846
for <mcox4@osf1.gmu.edu>; Mon, 16 Aug 1999 04:21:52 -0400 (EDT)
Received: (qmail 5141 invoked by alias); 16 Aug 1999 08:21:42 -0000
Received: (qmail 5134 invoked from network); 16 Aug 1999 08:21:41 -0000
Received: from unknown (HELO mr4.vic-remote.bigpond.net.au) (24.192.1.19) by pop.onelist.com with SMTP; 16 Aug 1999 08:21:41 -0000
Received: from bigpond.net.au (CPE-24-192-26-175.vic.bigpond.net.au [24.192.26.175]) by mr4.vic-remote.bigpond.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA19900 for <amos-list@onelist.com>; Mon, 16 Aug 1999 18:21:46 +1000 (EST)
> Your game will works as a small IRC client and not as server... you've to open a
> connection with a IRC server, and create a dedicated Channel for your
> game.. for example JBonds.
>
> When the players join the channel, your program will be informed, and you (..
> your program) are able to play (chat) with all the players or just some of them.
>
> For the protocol to use, you can be inspired by the other internet protocols like HTTP,FTP,IRC an so on. Just use simple ASCII commands... for example if you want to move a player you can send a command (message) like this:
>
> MOVE James,50,90
Oh yuck. That's all the Internet needs, more excessively verbose
protocols. It's not very Amiga either, to use 16 (plus IRC protocol)
bytes when 3 will do. You have replaced a simple Internet port
programming problem with a complex "first write an IRC client, then
write your protocol on top" problem.
Inetd is designed to listen on certain ports, and start a new instance
of a particular server proggy for each incoming connection. Since your
proggy still needs to do everything except listening for a connection,
you are probably better off simplifying things by just adding the
"listen for a connection" part yourself.
I can't solve this particular problem for you though, I don't even have
AMOS Internet extensions.
Oh, and do us all a favour, design a compact protocol that uses all 8
bits of the bandwidth, rather than having every 8th bit wasted. It's
well overdue that the Internet changed to 8 bit protocols instead of 7
bit protocols and all the encoding that has to go on to cater for
sending 8 bit data through a 7 bit protocol working over an 8 bit link.
This sort of madness probably wastes about one quarter of all available
bandwidth just on un-needed overhead. All to cater for some ancient
systems that probably only exist in museums now.
Sorry about that, it's a pet peeve of mine. All the reasons for using
innefficient protocols on the Internet went away a long time ago, and
most of then probably didn't exist when the bulk of protocols where
designed.
--
Look out your Windows, the Penguins are coming, and they've got Balls!
David Seikel dvs1 Digital Polyglot World's Greatest Programmer.
"Any sufficiently advanced magic is indistinguishable from technology."
